add task
Uses
<add task command> {[<property key> <property value>]}*
<add task command>- main command:
add task - aliases:
task add,make task,create task,task create,addtsk,mktsk - snippets:
+t,+ t,+ task
- main command:
ADD_TASK:
ADD_TASK ::= ( ( 'add' | 'create' ) SPC 'task'
| 'task' SPC ( 'add' | 'create' )
| 'addtsk'
| 'mktsk' ) ITEM_NAME? TASK_PTRS
Aliases and snippets help us input the command in the command line and automatically transform it into the main command. But if you call the command in API, then use only the main command
<property key>name|--name|-Nin domain|--domain|-domfor project|--project|-passigned to|deligate to|--assign|-adue|due on|deadline|deadline on|--due|--deadlinestart|start on|--start|-sfinish|finish on|--finish|-fduration|--duration|-dwith pritority|--priority|-Pwith constraints|--constraints|--constdepends on|--after|--berfore|--withrecurring|--repeat|-restimated time|--estimate|-enote|--note|-n
- The list of properties pair can be empty or have key-values spaces-separated pairs
- The default first key is
name, which can be skipped, then the value after the command name is identified as the value of thenamekey. If the first key after the command name is different, then you must use thenamekeyword to define the start of thenamevalue definition instruction. - The key-value pairs can be defined in any order
TASK_PTRS:
- name
- domain
- project
- assigned
- due
- start
- finish
- duration
- priority
- recuring
- note
name
ITEM_NAME:
ITEM_NAME ::= SPC ( '"' | "'" ) ANY_CHAR? ( '"' | "'" )
| ( SPC WORD )+
TASK_PTRS:
TASK_PTRS ::= ( SPC DOMAIN_PTR )?
( SPC PROJECT_PTR )?
( SPC ASSIGN_PTR )?
( SPC DUE_PTR )?
( SPC START_PTR )?
( SPC FINISH_PTR )?
( SPC PRIORITY_PTR )?
( SPC RECURRING_PTR )?
( SPC NOTE_PTR )?
( SPC NAME_PTR )?
add task New task
or
add task "New Task"
or
add task --name New task
or
add task --name "New task"
- The name's value can be enclosed in single or double quotes but can be without it (end with next keywords)
- If the name's value define immediately after the command name,
then we can omit keyword
name
in domain
DOMAIN_PTR:
DOMAIN_PTR ::= ( 'in' SPC 'domain' | '--domain' | '-dom' ) DOMAIN_NAME
add task <task name> in domain <domain's ID>
<domain's id>can be the name's of domain or ID which identify domain- default value of the domain is
Inbox
for project
PROJECT_PTR:
PROJECT_PTR ::= ( 'for' SPC 'project' | '--project' | '-p' ) PROJECT_NAME
add task <task name> for project <project's ID>
<project's ID>can be the name's of project or ID which identify project- default value of is not defined
assigned to
ASSIGN_PTR:
ASSIGN_PTR ::= ( ( 'assigned' | 'deligate' ) SPC 'to' | '--assign' | '-a' ) ASSIGN_LIST
add task <task name> assigned to <user's ID>
<user's ID>can be the name's of project or ID which identify user- default value of the assigned your is current user
due
DUE_PTR:
DUE_PTR ::= ( ( 'due' | 'deadline' ) ( SPC 'on' )? | '--due' | '--deadline' ) DEPENDS_RULES
DEPENDS_RULES:
DEPENDS_RULES
::= SPECIFIC_DATE
| DEPENDS_RELATION
| CONSTRAINTS
SPECIFIC_DATE:
SPECIFIC_DATE
::= 'on' ( SPEC_DATE | RELATED_DATE ) ( 'at' TIME )?
DEPENDS_RELATION:
DEPENDS_RELATION
::= 'today'
| 'tomorrow'
| 'on' ( 'mo' | 'tu' | 'we' | 'th' | 'fr' | 'sa' | 'su' )
CONSTRAINTS:
CONSTRAINTS
::= 'asap'
| 'alap'
| 'this' ( 'week' | 'month' | 'quarter' | 'year' )
| ( 'after' | 'before' ) SPECIFIC_DATE
add task <task name> due <depends>
<depends> := (<specific date> | <depends relation>)[ <constraints>]
<specific date> := (on <date> | <relative date>)[ at <time>]
<relative date> := today
| tomorrow
| on (mo | tu | we | th | fr | sa | su)
<constraints> := asap | alap
| this (week | month | quarter | year)
| after <specific date>
| before <speific date>
add task <task name> due on 2025-02-27-- must be done on 2025-02-27 at 23:59:59 or earlyadd task <task name> due on 2025-02-27 at 9:00-- must be done on 2025-02-27 at 9:00 (or early)add task <task name> due on mo-- must be done on next Monday at 23:59:59 (or early)add task <task name> due tomorrow--add task <task name> due asapadd task <task name> deadline before 2025-03-01
- All the relative dates will be changed to the specific dates before saving because this relative value makes sense only at the moment and is only for humans' comfortable uses
start
START_PTR:
START_PTR::= ( 'start' ( SPC 'on' )? | '--start' | '-s' ) DEPENDS_RULE
add task <task name> start <depends>
finish
FINISH_PTR:
FINISH_PTR ::= ( 'finish' ( SPC 'on' )? | '--finish' | '-f' ) DEPENDS_RULE
add task <task name> finish <depends>
duration
DURATION_PTR:
DURATION_PTR ::= ( 'duration' | '--duration' | '-d' ) DURATION_RULE
add task <taskname> duration <task duration>
<task duration> := <number>[[] <modifier> [estimated]]
<modifier> := m | min | minute | minutes
| h | hour | hours
| d | day | days
| mo | month | months
| q | quarter | quarters
| y | year | years
- after numbers can be a space, but it is not obligatory
- modifier of the duration's value can be short or long if you wish
- if you skip the modifier and use only number, then the modifier
automatically sets as
hwith flagestimated - default value is
1 h estimated
for example
add task The New Task duration 2
The New Task will have the duration equal 2 hours with flag estimated
add task The New Task duration 15m
The New Task will have the duration equal to 15 minutes
with priority
PRIORITY_PTR:
PRIORITY_PTR
::= ( 'with' SPC 'priority' | '--priority' | '-P' ) PRIORITY_VALUE
PRIORITY_VALUE:
PRIORITY_VALUE
::= '100'
| 'someday'
| 'maybe'
| ( '9' | '8' | '7' | '6' | '5' | '4' | '3' | '2' | '1' )? ( '9' | '8'
| '7' | '6' | '5' | '4' | '3' | '2' | '1' | '0' )
| 'low'
| 'normal'
| 'middle'
| 'high'
| 'top'
add task <taskname> with priority <priority's value>
<priority's value> := 100 | someday | maybe
| {71..99}
| 70 | low
| {51..69}
| 50 | normal | middle
| {2..49}
| 1 | high
| 0 | top
for example
add task The new Task with priority high
and the same
add task The new Task with priority 1
- the lover the number -- the higher the priority
- if the priority value is bigger than 100, then the priority set is 100
- default priority is normal
Uses examples
add task
Expected result: Open the Add task dialog (pop up)
add task Make the document
or
add task "Make the document"
or
add task 'Make the document'
Expected result: Task is made in the Inbox domain and selected like as current (changed contex and ready for other actions with them)
In this example we set Make the document as value of the property name.
The same result with:
task create Задача с полной информацией
for project "Проект Y"
in domain "Маркетинг"
assigned to "user3"
due on "2024-01-15"
depends on task 456
with constraints workdays only
recurring monthly
with priority medium
estimated time "3h"
note "Полное описание задачи"